Organize visualization files into structured subdirectories #117

codegen-sh · 2025-05-14T14:38:20Z

User description

Description

This PR organizes visualization-related files in the analyzers directory into a structured visualization subdirectory. The files are categorized based on their visualization types:

Directory Structure

call_graph/: Visualizations related to function call relationships and method interactions
- call_trace.py: Traces function call paths through a codebase
- graph_viz_call_graph.py: Creates directed call graphs for functions
- method_relationships.py: Visualizes relationships between methods in a class
- viz_cal_graph.py: Generates call graphs with detailed metadata
dependency_graph/: Visualizations related to code dependencies and impact analysis
- blast_radius.py: Shows the "blast radius" of changes to a function
- dependency_trace.py: Traces symbol dependencies through a codebase
- viz_dead_code.py: Identifies and visualizes dead/unused code
structure_graph/: Visualizations related to code structure and organization
- graph_viz_dir_tree.py: Displays directory structure as a graph
- graph_viz_foreign_key.py: Visualizes database schema relationships
docs/: Documentation and examples for visualization tools
- codebase-visualization.mdx: Comprehensive guide to codebase visualization

Changes

Created subdirectories for different visualization types
Moved existing visualization files to appropriate subdirectories
Added documentation explaining the organization
Moved codebase_visualizer.py to the visualization directory

This organization makes it easier to find and use the appropriate visualization tools for different purposes.

💻 View my work • About Codegen

Summary by Sourcery

Organize the visualization tools into structured subdirectories and update the core visualizer and CLI to work with the new layout.

Enhancements:

Create call_graph, dependency_graph, structure_graph, and docs subdirectories under analyzers/visualization and relocate existing files accordingly
Refactor CodebaseVisualizer to unify output formats, introduce VisualizationType and OutputFormat enums, and consolidate configuration into a dataclass
Simplify and strengthen the CLI by enforcing required arguments per visualization type and refining flags (e.g., severity choices)

Documentation:

Add comprehensive guide in docs/codebase-visualization.mdx
Introduce README.md summarizing the visualization directory structure and usage

Chores:

Update init.py modules and imports to match the new directory organization

PR Type

Enhancement, Documentation

Description

Refactored and unified the codebase visualization engine, introducing new enums (VisualizationType, OutputFormat) and a VisualizationConfig dataclass for consistent configuration.
Organized visualization-related files into structured subdirectories: call_graph, dependency_graph, structure_graph, and docs under analyzers/visualization.
Added new visualization modules and skills for call graphs, method relationships, function call tracing, blast radius, symbol dependencies, dead code, directory structure, and database foreign key relationships.
Implemented comprehensive test cases and detailed docstrings for visualization modules.
Enhanced documentation with a new README, module-level docstrings, and a detailed MDX guide covering usage, configuration, and workflows for visualization tools.
Updated the CLI and core visualizer to support the new structure and options.

Changes walkthrough 📝

Relevant files

Enhancement

10 files

codebase_visualizer.py `Refactor and unify codebase visualization engine with new features` codegen-on-oss/codegen_on_oss/analyzers/visualization/codebase_visualizer.py Major refactor and enhancement of the codebase visualizer module. Introduces new enums (`VisualizationType`, `OutputFormat`) and a `VisualizationConfig` dataclass for unified configuration. Implements comprehensive visualization methods for call graphs, dependency graphs, blast radius, class methods, module dependencies, dead code, cyclomatic complexity, issues heatmap, and PR comparison. Adds internal helpers for graph construction, plotting, and file output, and updates the CLI to support the new structure and options.	+1489/-198
graph_viz_call_graph.py `Add call graph visualization skills and test cases` codegen-on-oss/codegen_on_oss/analyzers/visualization/call_graph/graph_viz_call_graph.py Adds a new module for generating call graph visualizations using networkx. Implements three skills: call graph from node, call graph with filtering, and call paths between nodes. Includes test cases and detailed docstrings for each visualization skill.	+358/-0
method_relationships.py `Add class method relationship visualization script` codegen-on-oss/codegen_on_oss/analyzers/visualization/call_graph/method_relationships.py Adds a script to visualize relationships between methods in a class. Builds a directed graph of method calls within a class and their downstream calls. Includes configuration for node coloring and recursion depth.	+107/-0
viz_cal_graph.py `Add detailed call graph visualization with metadata` codegen-on-oss/codegen_on_oss/analyzers/visualization/call_graph/viz_cal_graph.py Adds a script to generate detailed call graphs with metadata for function calls. Supports configuration for ignoring external modules and class calls. Uses a color palette for node types and includes a sample entrypoint.	+121/-0
call_trace.py `Add function call trace and dependency visualization` codegen-on-oss/codegen_on_oss/analyzers/visualization/call_graph/call_trace.py Adds a script to trace function call paths and visualize symbol dependencies. Recursively builds a dependency graph for a target function. Includes configuration for recursion depth and node coloring.	+83/-0
blast_radius.py `Add blast radius visualization for function usages` codegen-on-oss/codegen_on_oss/analyzers/visualization/dependency_graph/blast_radius.py Adds a script to visualize the "blast radius" of changes to a function. Builds a graph of all usages of a target function, highlighting HTTP method handlers. Includes configuration for node coloring and recursion depth.	+119/-0
dependency_trace.py `Add symbol dependency trace visualization script` codegen-on-oss/codegen_on_oss/analyzers/visualization/dependency_graph/dependency_trace.py Adds a script to trace and visualize symbol dependencies in a codebase. Recursively builds a dependency graph for a target function. Includes configuration for recursion depth and node coloring.	+83/-0
viz_dead_code.py `Add dead code visualization skill and graph` codegen-on-oss/codegen_on_oss/analyzers/visualization/dependency_graph/viz_dead_code.py Adds a skill to visualize dead (unused) code in the codebase. Identifies dead code by finding functions with no usages and not in test files or decorated. Builds a graph of dead code and their dependencies.	+154/-0
graph_viz_dir_tree.py `Add directory tree structure visualization skill` codegen-on-oss/codegen_on_oss/analyzers/visualization/structure_graph/graph_viz_dir_tree.py Adds a skill to visualize the directory structure of a codebase as a graph. Iterates over files and builds a hierarchical graph of directories and files. Includes test cases for various directory structures.	+111/-0
graph_viz_foreign_key.py `Add foreign key relationship visualization for database models` codegen-on-oss/codegen_on_oss/analyzers/visualization/structure_graph/graph_viz_foreign_key.py Adds a skill to visualize SQLAlchemy model foreign key relationships as a graph. Parses model classes and their attributes to build a mapping of foreign key relationships. Highlights models with no inbound relationships and those mapping to a specific target.	+178/-0

Documentation

6 files

__init__.py `Add module docstring for call graph visualization package` codegen-on-oss/codegen_on_oss/analyzers/visualization/call_graph/init.py Adds an __init__.py file with a module-level docstring for call graph visualizations.	+6/-0
__init__.py `Add module docstring for dependency graph visualization package` codegen-on-oss/codegen_on_oss/analyzers/visualization/dependency_graph/init.py Adds an __init__.py file with a module-level docstring for dependency graph visualizations.	+6/-0
__init__.py `Add module docstring for structure graph visualization package` codegen-on-oss/codegen_on_oss/analyzers/visualization/structure_graph/init.py Adds an __init__.py file with a module-level docstring for structure graph visualizations.	+6/-0
__init__.py `Add module docstring for visualization documentation package` codegen-on-oss/codegen_on_oss/analyzers/visualization/docs/init.py Adds an __init__.py file with a module-level docstring for the visualization documentation package.	+6/-0
README.md `Add documentation for visualization directory structure and usage` codegen-on-oss/codegen_on_oss/analyzers/visualization/README.md Adds a comprehensive README describing the visualization directory structure and usage. Documents the purpose of each subdirectory and the types of visualizations provided. Lists the main visualization files and their roles.	+44/-0
codebase-visualization.mdx `Add detailed documentation for codebase visualization tools and` `workflows` codegen-on-oss/codegen_on_oss/analyzers/visualization/docs/codebase-visualization.mdx Added a comprehensive Markdown (MDX) documentation file for codebase visualization. Provides step-by-step guides for creating call trace, function dependency, and blast radius visualizations. Includes code examples, configuration tips, and embedded interactive graph iframes. Offers links to further tutorials and API references for extended learning.	+399/-0

Need help?
Type /help how to ... in the comments thread for any questions about Qodo Merge usage.
Check out the documentation for more information.

sourcery-ai · 2025-05-14T14:38:25Z

Reviewer's Guide

This PR restructures the visualization toolkit by grouping related scripts into dedicated subdirectories (call_graph, dependency_graph, structure_graph, docs), relocates existing modules accordingly, and modernizes the core CodebaseVisualizer with a unified graph-building API, new enums/configs, specialized visualize_* methods and updated CLI support, while adding comprehensive MDX documentation.

File-Level Changes

Change	Details	Files
Restructure visualization directory into logical subpackages	Create call_graph/, dependency_graph/, structure_graph/, and docs/ subdirectories Move existing visualization scripts into their respective folders Add init.py in each subdirectory to define modules Introduce a top-level README.md summarizing the new layout	`codegen_on_oss/analyzers/visualization/call_graph/call_trace.py` `codegen_on_oss/analyzers/visualization/call_graph/graph_viz_call_graph.py` `codegen_on_oss/analyzers/visualization/call_graph/method_relationships.py` `codegen_on_oss/analyzers/visualization/call_graph/viz_cal_graph.py` `codegen_on_oss/analyzers/visualization/dependency_graph/blast_radius.py` `codegen_on_oss/analyzers/visualization/dependency_graph/dependency_trace.py` `codegen_on_oss/analyzers/visualization/dependency_graph/viz_dead_code.py` `codegen_on_oss/analyzers/visualization/structure_graph/graph_viz_dir_tree.py` `codegen_on_oss/analyzers/visualization/structure_graph/graph_viz_foreign_key.py` `codegen_on_oss/analyzers/visualization/docs/codebase-visualization.mdx` `codegen_on_oss/analyzers/visualization/call_graph/__init__.py` `codegen_on_oss/analyzers/visualization/dependency_graph/__init__.py` `codegen_on_oss/analyzers/visualization/structure_graph/__init__.py` `codegen_on_oss/analyzers/visualization/docs/__init__.py` `codegen_on_oss/analyzers/visualization/README.md`
Overhaul core CodebaseVisualizer engine	Introduce VisualizationType and OutputFormat enums and a VisualizationConfig dataclass Unify graph setup and helper methods (_initialize_graph, _add_node, _add_edge, _generate_filename, save_visualization) Implement dedicated visualize* methods for call graphs, dependency graphs, blast radius, class methods, module dependencies, dead code, complexity, issues heatmap, and PR comparisons Remove separate AnalysisVisualizer and CodeVisualizer in favor of a single cohesive class	`codegen_on_oss/analyzers/visualization/codebase_visualizer.py`
Add comprehensive visualization documentation	Add MDX guide (codebase-visualization.mdx) with embedded examples and step-by-step tutorials Link interactive iframes for call graph, dependency graph, and blast radius demos Outline common use cases and next steps within docs	`codegen_on_oss/analyzers/visualization/docs/codebase-visualization.mdx`

Tips and commands

Interacting with Sourcery

Trigger a new review: Comment @sourcery-ai review on the pull request.
Continue discussions: Reply directly to Sourcery's review comments.
Generate a GitHub issue from a review comment: Ask Sourcery to create an
issue from a review comment by replying to it. You can also reply to a
review comment with @sourcery-ai issue to create an issue from it.
Generate a pull request title: Write @sourcery-ai anywhere in the pull
request title to generate a title at any time. You can also comment
@sourcery-ai title on the pull request to (re-)generate the title at any time.
Generate a pull request summary: Write @sourcery-ai summary anywhere in
the pull request body to generate a PR summary at any time exactly where you
want it. You can also comment @sourcery-ai summary on the pull request to
(re-)generate the summary at any time.
Generate reviewer's guide: Comment @sourcery-ai guide on the pull
request to (re-)generate the reviewer's guide at any time.
Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
pull request to resolve all Sourcery comments. Useful if you've already
addressed all the comments and don't want to see them anymore.
Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
request to dismiss all existing Sourcery reviews. Especially useful if you
want to start fresh with a new review - don't forget to comment
@sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

Enable or disable review features such as the Sourcery-generated pull request
summary, the reviewer's guide, and others.
Change the review language.
Add, remove or edit custom review instructions.
Adjust other review settings.

Getting Help

Contact our support team for questions or feedback.
Visit our documentation for detailed guides and information.
Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

korbit-ai · 2025-05-14T14:38:25Z

By default, I don't review pull requests opened by bots. If you would like me to review this pull request anyway, you can request a review via the /korbit-review command in a comment.

coderabbitai · 2025-05-14T14:38:27Z

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- Explain this complex logic.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
- @coderabbitai explain this code block.
- @coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @coderabbitai read src/utils.ts and explain its main purpose.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
- @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
@coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai configuration to show the current CodeRabbit configuration for the repository.
@coderabbitai help to get help.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

codegen-sh · 2025-05-14T14:39:09Z

Hey! 👋 I see one of the checks failed. I am on it! 🫡

💻 View my work

korbit-ai · 2025-05-14T14:41:42Z

By default, I don't review pull requests opened by bots. If you would like me to review this pull request anyway, you can request a review via the /korbit-review command in a comment.

codiumai-pr-agent-free · 2025-05-14T14:42:28Z

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 3 🔵🔵🔵⚪⚪
🧪 No relevant tests
🔒 No security concerns identified
⚡ Recommended focus areas for review Error Handling The error handling in _convert_graph_to_json() doesn't properly check for serializable types. The current implementation uses a pattern-matching approach with `isinstance(value, str \| int \| float \| bool \| list \| dict)` which may not catch all edge cases and could lead to serialization errors. if key not in ["name", "type", "color", "file_path", "original_node"]: if ( isinstance(value, str \| int \| float \| bool \| list \| dict) or value is None ): node_data[key] = value Missing Attributes The code references self.current_visualization_type and self.current_entity_name in multiple methods but these attributes are only set within specific visualization methods. If a method like _convert_graph_to_json() or _plot_graph() is called directly, these attributes might be undefined. "visualization_type": self.current_visualization_type, "entity_name": self.current_entity_name,

codiumai-pr-agent-free · 2025-05-14T14:44:32Z

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Prevent infinite recursion The `visited` dictionary is declared but never used in the code. This could lead to potential infinite recursion in the `create_dependencies_visualization` function when processing cyclic dependencies. Initialize and use this dictionary to track visited nodes. codegen-on-oss/codegen_on_oss/analyzers/visualization/dependency_graph/dependency_trace.py [21-22] # Dictionary to track visited nodes and prevent cycles -visited = {} +visited = set() +def create_dependencies_visualization(symbol: Symbol, depth: int = 0): + """Creates a visualization of symbol dependencies in the codebase + + Recursively traverses the dependency tree of a symbol (function, class, etc.) + and creates a directed graph representation. Dependencies can be either direct + symbol references or imports. + + Args: + symbol (Symbol): The starting symbol whose dependencies will be mapped + depth (int): Current depth in the recursive traversal + """ + if depth >= MAX_DEPTH or symbol in visited: + return + + visited.add(symbol) + Apply / Chat Suggestion importance[1-10]: 8 __ Why: The `visited` variable is declared but not used in the `create_dependencies_visualization` function in the PR. The suggestion to initialize it as a `set` and use it to track visited nodes correctly addresses a potential infinite recursion issue if `MAX_DEPTH` is insufficient for complex cyclic dependencies, significantly improving the function's robustness.	Medium
	Graceful dependency handling The error handling for missing dependencies is too aggressive. Instead of immediately exiting the program when visualization dependencies are missing, consider setting a flag to disable visualization features and continue with reduced functionality. This allows the module to be imported and used for non-visualization tasks. codegen-on-oss/codegen_on_oss/analyzers/visualization/codebase_visualizer.py [20-28] try: import matplotlib.pyplot as plt import networkx as nx from matplotlib.colors import LinearSegmentedColormap + VISUALIZATION_AVAILABLE = True except ImportError: print( "Visualization dependencies not found. Please install them with: pip install networkx matplotlib" ) - sys.exit(1) + VISUALIZATION_AVAILABLE = False Apply / Chat Suggestion importance[1-10]: 7 __ Why: The suggestion improves robustness by preventing the program from exiting if optional visualization dependencies are missing, allowing other functionalities to remain operational.	Medium
	Improve error handling Similar to the visualization dependencies, the error handling for missing SDK dependencies is too aggressive. Instead of exiting the program, consider raising a more specific exception that can be caught by calling code, allowing for better error handling and recovery. codegen-on-oss/codegen_on_oss/analyzers/visualization/codebase_visualizer.py [30-58] try: from codegen.sdk.core.class_definition import Class from codegen.sdk.core.codebase import Codebase from codegen.sdk.core.detached_symbols.function_call import FunctionCall from codegen.sdk.core.file import SourceFile from codegen.sdk.core.function import Function from codegen.sdk.core.import_resolution import Import from codegen.sdk.core.symbol import Symbol from codegen.sdk.enums import EdgeType, SymbolType from codegen_on_oss.codebase_analyzer import ( AnalysisType, CodebaseAnalyzer, Issue, IssueSeverity, ) # Import custom modules from codegen_on_oss.context_codebase import ( GLOBAL_FILE_IGNORE_LIST, CodebaseContext, get_node_classes, ) from codegen_on_oss.current_code_codebase import get_selected_codebase -except ImportError: + SDK_AVAILABLE = True +except ImportError as e: print( - "Codegen SDK or custom modules not found. Please ensure all dependencies are installed." + f"Codegen SDK or custom modules not found: {e}. Please ensure all dependencies are installed." ) - sys.exit(1) + SDK_AVAILABLE = False Apply / Chat Suggestion importance[1-10]: 7 __ Why: The suggestion enhances error handling by avoiding an abrupt program termination if SDK dependencies are missing, making the module more resilient and usable in environments with partial setups.	Medium
	Fix Python version compatibility The type checking syntax `isinstance(value, str \| int \| float \| bool \| list \|` `dict)` uses Python 3.10+ union operator syntax, which may cause compatibility issues with older Python versions. Replace with a more compatible approach using multiple types in a tuple. codegen-on-oss/codegen_on_oss/analyzers/visualization/codebase_visualizer.py [305-335] def _convert_graph_to_json(self): """ Convert the networkx graph to a JSON-serializable dictionary. Returns: Dictionary representation of the graph """ nodes = [] for node, attrs in self.graph.nodes(data=True): # Create a serializable node node_data = { "id": node, "name": attrs.get("name", ""), "type": attrs.get("type", ""), "color": attrs.get("color", "#BBBBBB"), } # Add file path if available if "file_path" in attrs: node_data["file_path"] = attrs["file_path"] # Add other attributes for key, value in attrs.items(): if key not in ["name", "type", "color", "file_path", "original_node"]: if ( - isinstance(value, str \| int \| float \| bool \| list \| dict) + isinstance(value, (str, int, float, bool, list, dict)) or value is None ): node_data[key] = value nodes.append(node_data) Apply / Chat Suggestion importance[1-10]: 7 __ Why: The suggestion ensures broader Python version compatibility by replacing Python 3.10+ specific type union syntax (`\|`) with a tuple-based approach for `isinstance`, preventing errors in older Python environments.	Medium
	Add missing staticmethod decorator The `skill_func` method is missing the `@staticmethod` decorator which is required since it's defined within a class but doesn't use `self`. This could lead to runtime errors when the method is called. codegen-on-oss/codegen_on_oss/analyzers/visualization/structure_graph/graph_viz_dir_tree.py [86-88] +@staticmethod @skill_impl(test_cases=[PyRepoDirTreeTest], language=ProgrammingLanguage.PYTHON) @skill_impl(test_cases=[], skip_test=True, language=ProgrammingLanguage.TYPESCRIPT) def skill_func(codebase: CodebaseType): Apply / Chat Suggestion importance[1-10]: 7 __ Why: The suggestion correctly identifies that the `skill_func` method, as shown in the `existing_code` (lines 86-88 of the new hunk), should be decorated with `@staticmethod` because it is part of a class but does not use `self`. Adding `@staticmethod` (as the PR does on line 85) prevents potential `TypeError` exceptions. The suggestion is technically sound.	Medium
More

codegen-sh · 2025-05-14T14:44:39Z

✅ Fixed the failing pre-commit check in this commit. The issue was related to TRY003 errors in the analyzer.py file, where exception messages were being specified outside the exception class. I've created custom exception classes and removed the inline error messages to fix the issue.

💻 View my work • React 👍 or 👎

Organize visualization files into structured subdirectories

02684b4

Zeeeepa marked this pull request as ready for review May 14, 2025 14:41

Zeeeepa merged commit 46ce872 into develop May 14, 2025
11 of 17 checks passed

codiumai-pr-agent-free bot added the Review effort 3/5 label May 14, 2025

Organize visualization files into structured subdirectories #117

Organize visualization files into structured subdirectories #117

Uh oh!

Conversation

codegen-sh bot commented May 14, 2025 • edited by codiumai-pr-agent-free bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

User description

Description

Directory Structure

Changes

Summary by Sourcery

PR Type

Description

Changes walkthrough 📝

Uh oh!

sourcery-ai bot commented May 14, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer's Guide

File-Level Changes

Interacting with Sourcery

Customizing Your Experience

Getting Help

Uh oh!

korbit-ai bot commented May 14, 2025

Uh oh!

coderabbitai bot commented May 14, 2025

Review skipped

Chat

Support

CodeRabbit Commands (Invoked using PR comments)

Other keywords and placeholders

CodeRabbit Configuration File (.coderabbit.yaml)

Documentation and Community

Uh oh!

codegen-sh bot commented May 14, 2025

Uh oh!

Uh oh!

korbit-ai bot commented May 14, 2025

Uh oh!

codiumai-pr-agent-free bot commented May 14, 2025

PR Reviewer Guide 🔍

Uh oh!

codiumai-pr-agent-free bot commented May 14, 2025

PR Code Suggestions ✨

Uh oh!

codegen-sh bot commented May 14, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

codegen-sh bot commented May 14, 2025 •

edited by codiumai-pr-agent-free bot

Loading

sourcery-ai bot commented May 14, 2025 •

edited

Loading

CodeRabbit Configuration File (`.coderabbit.yaml`)